This table holds an entry for each command that has been issued for each remote vault. It is used by the Meridian Enterprise export processor to send commands to remote vaults
The GCFCommands table contains the columns described in the following table.
Column | Description |
---|---|
Command |
The command to be executed at the vault specified in DestinationShare. This column should be set to the following string value: SCRIPT::<FunctionName> <Arguments> In this value, <FunctionName> is the name of the VBScript function to be executed and <Arguments> is the parameters list. The parameters in the list are separated by spaces (not commas). To include a parameter with embedded spaces, enclose it in double quotes (“”). |
ActionDate |
The date at which the command was scheduled for transfer. When setting this column from VBScript, set it to 0. |
GlobalID |
The Global ID value of the document for which the command should be executed or Null if the command should not be executed with a specific document. This is the Global ID of the document that will become the CurrentDocument object in the remote VBScript function. |
DocName |
The name of the document for which the command should be executed or Null if the command should not be executed with a specific document. This is the name of the document that will become the CurrentDocument object in the remote VBScript function. This column is optional and is used for troubleshooting. |
DestinationShare |
The share name of the remote vault in which to run the command. |
InTransit |
True if the command has been sent to the vault specified in DestinationShare. When setting this column from VBScript, set it to 0. |
Pending |
True if the command is still pending to be transferred to the vault specified in DestinationShare. If set to -1, the command is no longer pending |
Related concepts
Related tasks
Executing remote script functions
Related information